Starting Up

Here is a server startup checklist:

Create an icon for the server by dragging httpd.exe from the File Manager window to a Program Manager group window.
Make sure your WinSock package is running. The server will use DNS, if it is available, to identify itself and the hostnames of clients for logging.
Double-click the httpd icon. If DNS is not available, it will take up to 30 sec. to complete initialization (varies with the TCP/IP package).
Once the server has minimized itself to an icon, it is ready to go. Try opening the URL for your home page, which should be like this:
```
http://your.host.name/
```

Command Line Options

For more advanced situations, or if you experience network problems, you can use the following command line flags (which may be set in the command line property of the icon):

-d directory
This specifies a different Server Root than c:\httpd and controls where httpd will look for its configuration files.
-f file
This specifies a Server Configuration File for httpd to start up with.
-l DLLname
Load the specified DLL at server startup, unload it at server exit. Useful for keeping VBRUN300.DLL loaded if the server is used to service frequent requests needing Visual Basic programs that use the Windows CGI Interface.
-n
Disable all asynchronous network I/O. Use this if you are having network problems. It can help you discover if your WinSock package is broken. It disables multi-threading so use it only as a last resort.
-r
Enable DNS reverse lookups for clients. Required for hostname filtering access control. Puts host domain names instead of IP addresses into the Transfer Log.
-x 0xnnn
This specifies the types of events to trace. Each event type is represented by a bit. There is no configuration file directive for controlling tracing; it must be enabled via this command line option.

Return to the Installation Overview

Robert B. Denny <rdenny@netcom.com>